VCard Maker

💬
DocOps.ioMIT Licensehttps://docops.io2025-11-18 {"headers":["Label","Link","Description","Type","Color","Enabled","Active"],"rows":[["ADR","adr.html","Architecture Decision Records","documentation","#2563eb","true","false"],["Architecture","arch.html","DocOps Implementation Architecture","documentation","#2563eb","true","false"],["Buttons","buttons.html","Button Documentation","documentation","#2563eb","true","false"],["Callout","callout.html","Callout Documentation","documentation","#2563eb","true","false"],["Charts","charts.html","Charts Documentation","documentation","#2563eb","true","false"],["Connectors","connectors.html","Connector Documentation","documentation","#2563eb","true","false"],["DocOps Core","docops.html","DocOps Block Processor Documentation","documentation","#2563eb","true","false"],["Domain Visualization","domain.html","Domain Visualization Documentation","documentation","#2563eb","true","false"],["Examples","examples.html","Examples Documentation","documentation","#2563eb","true","false"],["Feature Cards","featurecard.html","Documentation to the tool for creating visually appealing, interactive feature cards","documentation","#2563eb","true","false"],["Flow","flow.html","Flow Diagrams","documentation","#2563eb","true","false"],["Gherkin","gherkin.html","Gherkin Format support for DocOps","documentation","#2563eb","true","false"],["Index","index.html","Index of all documentation","documentation","#2563eb","true","false"],["Metrics Card","metricscard.html","Metrics Card Documentation","documentation","#2563eb","true","false"],["Placemat","placemat.html","Placemat Documentation","documentation","#2563eb","true","false"],["Planner","planner.html","Project Planner Documentation","documentation","#2563eb","true","false"],["Quadrant","quadrant.html","Quadrant Chart Documentation","documentation","#2563eb","true","false"],["Release Strategy","releasestrategy.html","Release Strategy Documentation","documentation","#2563eb","true","false"],["Roadmap","roadmap.html","Roadmap Documentation","documentation","#2563eb","true","false"],["Scorecard","scorecard.html","Scorecard Documentation","documentation","#2563eb","true","false"],["Shield","shield.html","Shield Documentation","documentation","#2563eb","true","false"],["Story","story.html","What is DocOps","documentation","#2563eb","true","false"],["Swimlane","swimlane.html","Swimlane Documentation","documentation","#2563eb","true","false"],["Timeline","timeline.html","Timeline Documentation","documentation","#2563eb","true","false"],["Todo","todo.html","Todo Documentation","documentation","#2563eb","true","false"],["Tree Chart","treechart.html","Tree Chart Documentation","documentation","#2563eb","true","false"],["Tutorial","tutorial.html","Sample Tutorials","documentation","#2563eb","true","false"],["VCard","vcard.html","VCards","documentation","#ef4444","true","true"],["Word Cloud","wordcloud.html","Word Cloud Documentation","documentation","#2563eb","true","false"]]} Generated by DocOps.io - Licensed under MIT License TitleADRArchitectureButtonsCalloutChartsConnectorsDocOps CoreDomain VisualizationExamplesFeature CardsFlowGherkinIndexMetrics CardPlacematPlannerQuadrantRelease StrategyRoadmapScorecardShieldStorySwimlaneTimelineTodoTree ChartTutorialVCardWord Cloud

1. Introduction

The VCard Maker renders a clean, scannable contact card (SVG) from standard vCard 3.0 text. It’s great for team directories, speaker bios, internal wikis, and handoff documents. You write a tiny vCard block; DocOps turns it into a polished card with name, role, organization, phones, emails, and a compact QR code linking back to the card data.

2. Usage

Insert a block using the docops extension and the vcard type. For reusability, keep your vCard content in data files and include them.

[docops,vcard]
----
BEGIN:VCARD
VERSION:4.0
FN:Jordan A. Rivera
N:Rivera;Jordan;A.;Mr.;
ORG:Acme Solutions;Product Engineering
TITLE:Senior Engineering Manager
ROLE:Engineering Management
EMAIL;TYPE=work,preferred:jjrivera@acmesolutions.com
EMAIL;TYPE=personal:jordan.rivera@gmail.com
TEL;TYPE=work,voice,preferred:+1-415-555-0123
TEL;TYPE=work,fax:+1-415-555-0140
TEL;TYPE=cell:+1-415-555-0199
TEL;TYPE=home:+1-415-555-0166
ADR;TYPE=work;LABEL="Acme Solutions\n123 Market St\nSuite 400\nSan Francisco, CA 94105\nUSA":;;123 Market St;San Francisco;CA;94105;USA
ADR;TYPE=home;LABEL="Home\n456 Oak Ave\nApt 2B\nOakland, CA 94607\nUSA":;;456 Oak Ave;Oakland;CA;94607;USA
URL;TYPE=work:https://www.acmesolutions.com
IMPP;TYPE=work:xmpp:jrivera@acmesolutions.com
X-SOCIALPROFILE;TYPE=twitter:https://twitter.com/jordanrivera
X-SOCIALPROFILE;TYPE=linkedin:https://www.linkedin.com/in/jordanrivera
X-SOCIALPROFILE;TYPE=facebook:https://www.facebook.com/jordan.rivera
BDAY:1985-07-14
REV:2025-11-07T12:00:00Z
NOTE:Primary contact for product engineering and cross-functional initiatives.
END:VCARD
----

2.1. Default

DocOps.ioMIT Licensehttps://docops.io2025-11-18 {"headers":[],"rows":[]} Generated by DocOps.io - Licensed under MIT LicenseJordan RiveraSenior Engineering ManagerAcme Solutionsjjrivera@acmesolutions.com+1-415-555-0123Scan for all info

2.2. Business Card

DocOps.ioMIT Licensehttps://docops.io2025-11-18 {"headers":[],"rows":[]} Generated by DocOps.io - Licensed under MIT LicenseJRJordan RiveraSenior Engineering ManagerAcme Solutionsjjrivera@acmesolutions.com+1-415-555-0123Scan for all info

2.3. Tech Pattern

DocOps.ioMIT Licensehttps://docops.io2025-11-18 {"headers":[],"rows":[]} Generated by DocOps.io - Licensed under MIT LicenseJordan Rivera<Senior Engineering Manager/>Acme Solutions$ contact --emailjjrivera@acmesolutions.com$ contact --phone-work+1-415-555-0123$ scan

2.4. Business Card Template

DocOps.ioMIT Licensehttps://docops.io2025-11-18 {"headers":[],"rows":[]} Generated by DocOps.io - Licensed under MIT LicenseJRJordanRiveraSenior Eng...Acme SolutionsProduct EngineeringEMAILjjrivera@acmesolutions.comWORK+1-415-555-0123Scan for full contact

3. Designs

The VCard Maker supports multiple design templates and a light/dark theme. Choose a design via a small config header placed before your vCard content, separated by ---.

Supported designs:

  • tech_pattern_background — Tech motif background with contrast blocks; pairs well with theme=dark

  • business_card_design — Classic business look (default if not specified)

  • business_card_design2 — Modern variant of the classic business card

  • business_card_template — Minimal template with clear information areas

  • creative_agency_pro_contact_card — Playful, agency-style layout with bold accents

  • modern_card — Contemporary, airy layout with generous spacing

Themes:

  • theme=light (default)

  • theme=dark

Example selector usage:

[docops,vcard]
----
design=tech_pattern_background
theme=dark
---
BEGIN:VCARD
VERSION:4.0
FN:Jordan A. Rivera
N:Rivera;Jordan;A.;Mr.;
ORG:Acme Solutions;Product Engineering
TITLE:Senior Engineering Manager
ROLE:Engineering Management
EMAIL;TYPE=work,preferred:jjrivera@acmesolutions.com
EMAIL;TYPE=personal:jordan.rivera@gmail.com
TEL;TYPE=work,voice,preferred:+1-415-555-0123
TEL;TYPE=work,fax:+1-415-555-0140
TEL;TYPE=cell:+1-415-555-0199
TEL;TYPE=home:+1-415-555-0166
ADR;TYPE=work;LABEL="Acme Solutions\n123 Market St\nSuite 400\nSan Francisco, CA 94105\nUSA":;;123 Market St;San Francisco;CA;94105;USA
ADR;TYPE=home;LABEL="Home\n456 Oak Ave\nApt 2B\nOakland, CA 94607\nUSA":;;456 Oak Ave;Oakland;CA;94607;USA
URL;TYPE=work:https://www.acmesolutions.com
IMPP;TYPE=work:xmpp:jrivera@acmesolutions.com
X-SOCIALPROFILE;TYPE=twitter:https://twitter.com/jordanrivera
X-SOCIALPROFILE;TYPE=linkedin:https://www.linkedin.com/in/jordanrivera
X-SOCIALPROFILE;TYPE=facebook:https://www.facebook.com/jordan.rivera
BDAY:1985-07-14
REV:2025-11-07T12:00:00Z
NOTE:Primary contact for product engineering and cross-functional initiatives.
END:VCARD
----

4. Examples

4.1. 1) Product PM (basic)

[docops,vcard]
----
BEGIN:VCARD
VERSION:4.0
FN:Jordan A. Rivera
N:Rivera;Jordan;A.;Mr.;
ORG:Acme Solutions;Product Engineering
TITLE:Senior Engineering Manager
ROLE:Engineering Management
EMAIL;TYPE=work,preferred:jjrivera@acmesolutions.com
EMAIL;TYPE=personal:jordan.rivera@gmail.com
TEL;TYPE=work,voice,preferred:+1-415-555-0123
TEL;TYPE=work,fax:+1-415-555-0140
TEL;TYPE=cell:+1-415-555-0199
TEL;TYPE=home:+1-415-555-0166
ADR;TYPE=work;LABEL="Acme Solutions\n123 Market St\nSuite 400\nSan Francisco, CA 94105\nUSA":;;123 Market St;San Francisco;CA;94105;USA
ADR;TYPE=home;LABEL="Home\n456 Oak Ave\nApt 2B\nOakland, CA 94607\nUSA":;;456 Oak Ave;Oakland;CA;94607;USA
URL;TYPE=work:https://www.acmesolutions.com
IMPP;TYPE=work:xmpp:jrivera@acmesolutions.com
X-SOCIALPROFILE;TYPE=twitter:https://twitter.com/jordanrivera
X-SOCIALPROFILE;TYPE=linkedin:https://www.linkedin.com/in/jordanrivera
X-SOCIALPROFILE;TYPE=facebook:https://www.facebook.com/jordan.rivera
BDAY:1985-07-14
REV:2025-11-07T12:00:00Z
NOTE:Primary contact for product engineering and cross-functional initiatives.
END:VCARD
----
DocOps.ioMIT Licensehttps://docops.io2025-11-18 {"headers":[],"rows":[]} Generated by DocOps.io - Licensed under MIT LicenseJordan RiveraSenior Engineering ManagerAcme Solutionsjjrivera@acmesolutions.com+1-415-555-0123Scan for all info
[docops,vcard]
----
design=creative_agency_pro_contact_card
BEGIN:VCARD
VERSION:4.0
FN:Jordan A. Rivera
N:Rivera;Jordan;A.;Mr.;
ORG:Acme Solutions;Product Engineering
TITLE:Senior Engineering Manager
ROLE:Engineering Management
EMAIL;TYPE=work,preferred:jjrivera@acmesolutions.com
EMAIL;TYPE=personal:jordan.rivera@gmail.com
TEL;TYPE=work,voice,preferred:+1-415-555-0123
TEL;TYPE=work,fax:+1-415-555-0140
TEL;TYPE=cell:+1-415-555-0199
TEL;TYPE=home:+1-415-555-0166
ADR;TYPE=work;LABEL="Acme Solutions\n123 Market St\nSuite 400\nSan Francisco, CA 94105\nUSA":;;123 Market St;San Francisco;CA;94105;USA
ADR;TYPE=home;LABEL="Home\n456 Oak Ave\nApt 2B\nOakland, CA 94607\nUSA":;;456 Oak Ave;Oakland;CA;94607;USA
URL;TYPE=work:https://www.acmesolutions.com
IMPP;TYPE=work:xmpp:jrivera@acmesolutions.com
X-SOCIALPROFILE;TYPE=twitter:https://twitter.com/jordanrivera
X-SOCIALPROFILE;TYPE=linkedin:https://www.linkedin.com/in/jordanrivera
X-SOCIALPROFILE;TYPE=facebook:https://www.facebook.com/jordan.rivera
BDAY:1985-07-14
REV:2025-11-07T12:00:00Z
NOTE:Primary contact for product engineering and cross-functional initiatives.
END:VCARD
----
DocOps.ioMIT Licensehttps://docops.io2025-11-18 {"headers":[],"rows":[]} Generated by DocOps.io - Licensed under MIT LicenseJordan RiveraSenior Engineering ManagerAcme Solutions@jjrivera@acmesolutions.com+1-415-555-0123Scan me!

4.2. 2) Research Scientist (multiple channels)

[docops,vcard]
----
BEGIN:VCARD
VERSION:3.0
FN:Aria Nova
N:Nova;Aria;L.;Dr.;PhD
ORG:Stellar Labs
TITLE:Principal Research Scientist
TEL;TYPE=cell,voice:+1-415-555-0420
TEL;TYPE=work,voice:+1-415-555-0421
EMAIL;TYPE=internet:aria.nova@stellarlabs.ai
EMAIL;TYPE=internet:research@stellarlabs.ai
URL:https://aria.nova.example.org
NOTE:Explores human-AI collaboration at planet scale. Loves synthwave and telescopes.
END:VCARD
----
DocOps.ioMIT Licensehttps://docops.io2025-11-18 {"headers":[],"rows":[]} Generated by DocOps.io - Licensed under MIT LicenseAria NovaPrincipal Research ScientistStellar Labsaria.nova@stellarlabs.ai+1-415-555-0420Scan for all info

4.2.1. Modern

DocOps.ioMIT Licensehttps://docops.io2025-11-18 {"headers":[],"rows":[]} Generated by DocOps.io - Licensed under MIT LicenseAria NovaPrincipal Research ScientistMobile+1-415-555-0420Emailaria.nova@stellarlabs.aiWebsitearia.nova.example.orgScan to save(click to enlarge)Explores human-AI collaboration atplanet scale. Loves synthwave andtelescopes.

4.3. 3) Minimal contact

[docops,vcard]
----
BEGIN:VCARD
VERSION:3.0
FN:Mo Lee
N:Lee;Mo;;;
EMAIL;TYPE=internet:mo@example.net
END:VCARD
----
DocOps.ioMIT Licensehttps://docops.io2025-11-18 {"headers":[],"rows":[]} Generated by DocOps.io - Licensed under MIT LicenseMo Leemo@example.netScan for all info

4.4. 4) International profile

[docops,vcard]
----
BEGIN:VCARD
VERSION:3.0
FN:Sofia García
N:García;Sofia;;;
ORG:Globex Internacional
TITLE:Directora de Producto
TEL;TYPE=cell,voice:+34 600 123 456
EMAIL;TYPE=internet:sofia.garcia@globex.es
ADR;TYPE=work:;;Calle de Alcalá 123;Madrid;Madrid;28009;España
URL:https://globex.es/people/sofia
NOTE:Habla Español, Inglés y Portugués. Amante del café y de los mapas antiguos.
END:VCARD
----
DocOps.ioMIT Licensehttps://docops.io2025-11-18 {"headers":[],"rows":[]} Generated by DocOps.io - Licensed under MIT LicenseSofia GarcíaDirectora de ProductoGlobex Internacionalsofia.garcia@globex.es+34 600 123 456Scan for all info

5. Attributes

  • design: Optional; selects the visual template. One of:

    • tech_pattern_background,

    • business_card_design,

    • business_card_design2,

    • business_card_template,

    • creative_agency_pro_contact_card,

    • modern_card. Defaults to business_card_design when omitted or invalid.

  • theme: Optional; light or dark. Defaults to light.

  • scale: Optional numeric factor to scale the rendered SVG. Defaults to 1.0.

Notes on styling: - Colors, typography, and layout follow the chosen design and theme. Designs may emphasize different typography, spacing, or accents, while theme adjusts contrast.

6. Tips for great cards

  • Prefer FN (Formatted Name) and N (structured name) together so names render crisply and sort correctly.

  • Keep TITLE concise (e.g., Principal Engineer vs Principal Engineer — Platform Reliability) and move details to NOTE.

  • Include at least one EMAIL or TEL; the card will adapt gracefully if one is missing.

  • Use URL to link a profile or docs page; the QR encodes the vCard so mobile users can save the contact quickly.

7. Notes

  • The input format is vCard 3.0 lines inside the block body. The maker supports FN, N, ORG, TITLE, TEL, EMAIL, URL, NOTE and gracefully ignores unknown properties.

  • For maintainability, keep vCard blocks in data files and include them, so the same card can be reused across adoc pages.

📖 3 min read • 1141 words